home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000465_news@columbia.edu _Sun Mar 23 13:04:31 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA13419
for <kermit.misc@watsun.cc.columbia.edu>; Sun, 23 Mar 1997 13:04:31 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA06995
for kermit.misc@watsun; Sun, 23 Mar 1997 13:04:29 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: k95 native windows update?
Date: 23 Mar 1997 18:04:26 GMT
Organization: Columbia University
Lines: 59
Message-ID: <5h3rba$dla$1@apakabar.cc.columbia.edu>
References: <u913eldq2.fsf@worldnet.att.net>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6797
In article <u913eldq2.fsf@worldnet.att.net>,
Thomas A. Horsley <Tom.Horsley@worldnet.att.net> wrote:
: I see no one has asked for a while when the native windows version of k95
: will show up, so I figured I'd go ahead and take the plunge this time :-).
:
Not to pick nits, but K95 has always been a 100% native 32-bit Windows 95
and NT application. The fact that it runs in a console window does not mean
it is not native. If it was not a native application, it would not run in
multiple threads, use 32-bit Winsock, understand long filenames, access the
system through 32-bit APIs and drivers, etc.
So to be precise, we are talking about the conversion of an already fully
native console program to a full-GUI (graphical user interface) application
of the sort that most Windows users expect to see.
: I dimly recall that March was once mentioned as a possible time frame,
: and since March has just about run out, I thought I'd ask how its going.
:
: So: Hows it going?
:
It's a long, slow, laborious process but there is progress. You can see
some preview screen shots at:
http://www.columbia.edu/kermit/kuishots.html
For the past few weeks we've been concentrating on TAPI (Microsoft's
telephony interface, which allows multiple applications to share the same
modem) and we seem to have it working.
For the benefit of those who wonder why this is taking so long... Unlike
other software makers, we produce applications for many platforms, not just
for Windows. Therefore we try to write portable code and share it among
many versions. It's no secret that Kermit 95's command/scripting language
and its file-transfer module are built from the same code base as C-Kermit
(for UNIX, VMS, etc). And even the terminal emulation / networking / file
and communications i/o that you see in Windows 95 and NT are also now
shared with the OS/2 version of Kermit 95. This was no simple feat, given
the lengths to which the Windows development model is designed to
discourage, if not defeat, portability.
We are not going to sacrifice our coverage of all those so-called "legacy"
platforms in order to rush the full-GUI version of Kermit 95 to market.
We'd all suffer in the long run if we did that. Remember, one of the
greatest strengths of Kermit software is that it is available for so many
platforms -- all of our Kermit programs are fully interoperable, and the
command and scripting languages are compatible across hundreds of different
platforms. Unlike practically any other maker of communications software,
we take care of both ends of the connection, not just the PC end.
To answer your question -- it doesn't look as if it will be ready in March,
or even April. Given the incredible number of roadblocks we run into at
every turn, we have given up on setting tentative release dates. But yes,
we are working on it full time, and the end is in sight.
(And no, we do not plan to also discontinue the console version when the
GUI version comes out -- believe it or not, many people have urged us to
always keep a current console version available, because they prefer it.)
- Frank